Method for delivering user input, and device using same

ABSTRACT

Provided is a method of delivering a user input received from a Human Interface Device (HID) to a source device by a sink device. The method includes: receiving the user input from the HID; generating HID user input information including a first field that represents a type of the HID, a second field that represents an interface type of the HID, and a third field that includes the user input received from the HID; and transmitting the configured HID user input information to the source device.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority under 35 U.S.C. 119 and 35U.S.C. 365 to U.S. provisional Application Nos. 61/433,942 (filed onJan. 18, 2011), 61/446,499 (filed on Feb. 25, 2011) and 61/583,143(filed on Sep. 23, 2011), which are hereby incorporated by reference inits entirety.

BACKGROUND

The present disclosure relates to a network wirelessly connecting aplurality of devices, and more particularly, to a method of delivering auser input received from a human interface to a sink device into asource device.

A variety of wireless communication technologies have been developedalong with the development of information communication technology.Among the wireless communication technologies, WLAN is a technology thatallows portable terminals such as a personal digital assistant (PDA), alaptop computer, and a portable multimedia player (PMP) to wirelesslyaccess a high-speed internet in a home or a business or specific servicearea, on the basis of wireless frequency technology.

For example, communication on the WLAN based on the IEEE 802.11 standardmay be provided in a basic service set (BSS) including an access point(AP) and a distribution system. Moreover, recently, as a wirelessshort-range communication technology is widely applied to a market, aP2P wireless communication method for direct connection between deviceswithout an AP is being developed.

SUMMARY

Embodiments provide a method and device for efficiently delivering auser input received from a human interface device.

In one embodiment, provided is a method of delivering a user inputreceived from a Human Interface Device (HID) to a source device by asink device. The method includes: receiving the user input from the HID;generating HID user input information including a first field thatrepresents a type of the HID, a second field that represents aninterface type of the HID, and a third field that includes the userinput received from the HID; and transmitting the configured HID userinput information to the source device.

In another embodiment, provided is a sink device delivering a user inputreceived from a Human Interface Device (HID) to a source device. Thesink device includes: a user interface unit receiving the user inputfrom the HID; a control unit generating HID user input informationincluding a first field that represents a type of the HID, a secondfield that represents an interface type of the HID, and a third fieldthat includes the user input received from the HID; and a wirelesstransmitting/receiving unit transmitting the generated HID user inputinformation to the source device.

Moreover, A non-transitory computer readable recording medium having aprogram recorded thereon, which, when executed by a computer, implementsthe user input delivery method.

According to an embodiment of the present invention, while a sink devicedelivers a user input, which is received from an HID, to a sourcedevice, the user input is packetized using a format received from theHID without additional conversion, and then, is transmitted to thesource device. Therefore, response delay for the user input may bereduced, and also, a load of the sink device may be reduced.

According to another embodiment of the present invention, since the userinput is delivered to the source device in addition to information onthe HID, the user input may be efficiently processed.

The details of one or more embodiments are set forth in the accompanyingdrawings and the description below. Other features will be apparent fromthe description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a configuration of a displaysystem according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating configurations of devicesaccording to an embodiment of the present invention.

FIG. 3 is a block diagram illustrating configurations of devicesaccording to another embodiment of the present invention.

FIG. 4 is a view illustrating a user input delivering method accordingto an embodiment of the present invention.

FIGS. 5 to 8 are views illustrating a configuration of HID user inputinformation according to a first embodiment of the present invention.

FIGS. 9 to 11 are views illustrating a configuration of HID user inputinformation according to a second embodiment of the present invention.

FIG. 12 is a block diagram illustrating operations for delivering a userinput of a source device, a sink device, and HIDs according to a firstembodiment of the present invention.

FIG. 13 is a view illustrating a format of HID user input informationtransmitted to a source device according to a first embodiment of thepresent invention.

FIG. 14 is a block diagram illustrating operations for delivering a userinput of a source device, a sink device, and HIDs according to a secondembodiment of the present invention.

FIG. 15 is a view illustrating a format of HID user input informationtransmitted to a source device according to a second embodiment of thepresent invention.

FIG. 16 is a view illustrating a format of HID user input informationtransmitted to a source device according to a third embodiment of thepresent invention.

FIG. 17 is a view illustrating a format of HID user input informationtransmitted to a source device according to a fourth embodiment of thepresent invention.

FIG. 18 is a view illustrating a format of HID user input informationtransmitted to a source device according to a fifth embodiment of thepresent invention.

FIG. 19 is a view illustrating a format of HID user input informationtransmitted to a source device according to a sixth embodiment of thepresent invention.

FIG. 20 is a block diagram illustrating operations for delivering a userinput of a source device, a sink device, and HIDs according to a thirdembodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Hereinafter, a user input delivering method and a device using the samewill be described in more detail with reference to FIGS. 1 to 20.

Hereinafter, detailed descriptions related to well-known functions orconfigurations will be ruled out in order not to unnecessarily obscuresubject matters of the present invention. Moreover, terms describedbelow are defined in consideration of the functions of the presentinvention and vary according to users, operators' intentions, orcustoms. Therefore, the definition may be determined based on the entirecontents of this specification.

FIG. 1 is a block diagram illustrating a configuration of a displaysystem according to an embodiment of the present invention. The displaysystem may include a source device 10, a sink device 20, and a humaninterface device (HID) 30.

Referring to FIG. 1, the source device 10 and the sink device 20configure a display group to transmit and receive multimedia contentsuch as video and audio and control signals through interconnectedsessions.

That is, the source device 10 transmits multimedia content to the sinkdevice 20 through the interconnected session, and for this, may have awireless LAN interface for streaming the multimedia content to the sinkdevice 20.

In addition, the sink device 20 may receive and play the multimediacontent transmitted from the source device 10 through the interconnectedsession.

Here, each of the source device 10 and the sink device 20 may be one ofvarious devices such as TVs, home theater systems, mobile phones, andtablet PCs. Also, each of them 10 and 20 may be divided into a sourceand a sink according to hardware or software functions, or may supportboth source and sink roles.

For example, a wireless connection between the source device 10 and thesink device 20 may use a 5 GHz frequency band according to the IEEE802.11ac, i.e., a Wi-Fi standard, and in this case, the source device 10may stream an uncompressed High Definition (HD) video at a speed of upto 1 Gbps.

However, the present invention is not limited to the above wirelesscommunication type, and may be implemented using various communicationtypes, for example, a 60 GHz frequency band according to the IEEE802.11ad standard.

The source device 10 and the sink device 20 belonging to one displaygroup may be connected using a P2P connection type or a Tunneled DirectLink Setup (TDLS) connection type.

For example, the source device 10 and the sink device 20 may configure anetwork, i.e., a P2P group, without an access point (AP), on the basisof the 802.11 WLAN techniques, and then communicate data via a directlink. In this case, any one of the source device 10 and the sink device20, as a group owner (GO), may perform a similar operation to the AP soas to manage the P2P group.

At the same time, each of the source device 10 and the sink device 20may be connected to and communicated with an infrastructure BSSincluding an AP and a distribution system.

Moreover, the source device 10 and the sink device 20 may selectivelyconnect to a session by using the TDLS. In this case, the source device10 and the sink device 20 may connect to one AP and communicate witheach other.

The HID 30, as a device for interface with a user, may convert a userinput according to a specific format and then transmit the converteduser input to the sink device 20.

For example, the HID 30 may be an input device such as a remotecontroller or one of various user input devices such as a touch panel, atouch keyboard, motion recognition, QWERTY remote control, a mouse, atrackball, and a joystick.

According to the universal series bus (USB) standard, devices may beclassified in to a class such as a display device, a communicationdevice, an audio device, a high capacity storage device, or the HID 30according to the nature of data.

Additionally, the HID 30 may be a convergence device that is used as adisplay device or communication device such as a smart phone or a tabletPC, and the HID 30 simultaneously.

Moreover, an interface and frame that the HID 30 uses may be definedaccording to various standards.

For example, an infrared interface for TV remote control, a Bluetoothinterface for a wireless keyboard or mouse, a USB interface for a wiredinterface device or wireless device, a Wi-Fi interface for IP basedcontrol through smart phone application or infrastructure, and a ZigBeeinterface for home appliance or factory automation may be used as aninterface type of the HID 30.

In a display system using a wireless network as shown in FIG. 1, thesink device 20 delivers a user input received from the HID 30 to thesource device 10, and then, the source device 10 executes an operation(for example, UI display) according to the user input.

For this, a session control such as play, pause, or auto routing may bedefined between the source device 10 and the sink device 20, and thismay be transmitted by a session control action frame.

Moreover, the sink device 20 may deliver a command in an action frameformat to the source device 10 by using a profile of an HDMI CECcommand.

FIG. 2 is a block diagram illustrating configurations of devicesaccording to a first embodiment of the present invention. That is, FIG.2 illustrates each configuration of the source device 10 and the sinkdevice 20 shown in FIG. 1.

Referring to FIG. 2, the source device 10 may include atransmitting/receiving unit 11, a control unit 12, and an AV codec 13.The sink device 20 may include a transmitting/receiving unit 21, acontrol unit 22, an AV codec 23, and a user interface unit 24.

Moreover, the transmitting/receiving units 11 and 21 maytransmit/receive frames in a format set according to a communicationstandard to perform a session connection between the source device 10and the sink device 20, including transport and network layers.

The transmitting/receiving unit 11 in the source device 10 may transmitmultimedia content to the sink device 20 via a connected session throughthe above processes, and the transmitting/receiving unit 22 in the sinkdevice 20 may receive the multimedia transmitted from the source device10.

Also, the control units 12 and 22 may perform processes such as devicesearch, service search, and device pairing on the basis of informationin the frames transmitted/received through the transmitting/receivingunits 11 and 21, and thus, may connect and manage a session between thesource device 10 and sink device 20.

For this, the control units 12 and 22 may include a MAC layer and a PHYlayer and the MAC/PHY layers may support a communication standard suchas 802.11, Wi-Fi Direct, or TDLS.

Or, the sink device 20 may configure a UI autonomously or according toUI information received from the source device 10 in the case of aremote UI, and then may display it on a screen.

For example, the control unit 22 of the sink device may configure a UIby using operating system (OS) and software (SW), and then may displayit through a display module (not shown) provided in or connected to thesink device 20.

The AV codecs 13 and 23 may encode or decode the multimedia contenttransmitted/received through a session between the source device 10 andthe sink device 20.

For example, the AV codec 13 in the source device 10 encodes video andaudio signals to be transmitted to the sink device 20, and the AV codec23 in the sink device 20 decodes the video and audio signals transmittedfrom the source device 10.

Moreover, the HID 30 may deliver a user input the sink device 20 throughan interface such as Infrared, Bluetooth, USB, Wi-Fi, or ZigBee. Forexample, the sink device 20 may receive a user input from the HID 30through the user interface unit 24.

In this case, the HID 30 connected to the sink device 20 may notcommunicate with the source device 10, and the sink device 20 mayconfigure or change a UI through the control unit 22 according to a userinput received from the HID 30.

The sink device 20 may deliver information on a user input inputteddirectly or received from the HID 30 to the source device 10 through useof an action frame.

Referring to FIG. 3, the source device 10 may configure a UI and displayit on a screen, and may transmit the displayed UI to the sink device 20in addition to multimedia content through a session connected to thesink device 20.

For example, a UI screen configured with OS/SW of the control unit 22may be multiplexed with multimedia content to be transmitted to the sinkdevice 20, and then may be delivered to the sink device 20 through oneTransport Stream (TS).

Additionally, the configured UI screen and the multimedia content aredelivered to the sink device 20 via additional TS, and the sink device20 may overlay the UI screen delivered via the additional TS with themultimedia content and then, may display it on a screen.

As show in FIG. 3, the sink device 20 converts a user input receivedfrom the HID 30 and delivers it to the source device 10 through a userinput back channel (UIBC).

For this, the sink device 20 may include a converter for generating anaction frame by parsing a user input received from the HID 30. It isnecessary to define a structure and interface for parsing an actionframe received from the sink device 20 at the source device 10 anddelivering it to OS/SW.

In this case, through processes such as the parsing and conversion ofthe sink device 20 and the parsing and UI encoding of the source device10 for the user input, response delay to the user input occurs.Therefore, long latency may be required until a user confirms theapplication of a corresponding input.

According to an embodiment of the present invention, the sink device 20may packetize a user input received from the HID 30 according to thereceived format as it is without additional conversion, and then, maytransmit it to the source device 10. Therefore, a response delay to theuser input and the load of the source device 10 and the sink device 20may be reduced.

The configurations of the source device 10 and the sink device 20described with reference to FIGS. 2 and 3 are just one example, andthus, the present invention is not limited thereto. Therefore, thesource device 10 or the sink device 20 may omit some of the componentsshown in FIG. 2 or 3 or may further include additional componentsaccording to a function of a corresponding device.

FIG. 4 is a view illustrating a user input delivering method accordingto an embodiment of the present invention. Description of the samemethod as that described with reference to FIGS. 1 to 3 among user inputdelivering methods below will be omitted.

Referring to FIG. 4, the sink device 20 receives a user input from theHID 30 in operation S100, and generates HID user input informationincluding the received user input in operation 5110.

For example, the HID user input information may include a first fieldrepresenting the type of the HID 30, a second field representing theinterface type of the HID 30, and a third field including a user inputreceived from the HID 30.

Then, the sink device 20 transmits the generated HID user inputinformation to the source device 10 in operation S120.

Referring to FIG. 5, the HID user input information may include an HIDcommand action frame including ‘Subelement ID’, ‘Length’, ‘HID ID’, ‘HIDinterface type’, ‘HID device type’, and ‘HID value’ fields.

The ‘Subelement ID’ field represents the type of a corresponding subelement, and the ‘Length’ field represents the length of the next fieldsin the corresponding sub element.

Also, the position of the ‘Length’ field is changeable, and when itsposition is changed in a frame, the ‘Length’ field represents the lengthof the next fields from a corresponding position.

Moreover, the ‘HID ID’ field, as information for identifying the HID 30,represents a globally unique identifier or a locally unique identifierfor the HID 30.

The ‘HID interface type’ field represents the type of an interface thatthe HID 30 uses. As shown in FIG. 6, according to an interface type ofthe HID 30, the ‘HID interface type’ field may have a valuecorresponding to one of infrared, USB, Bluetooth, ZigBee, Wi-Fi, andConsumer Electronics Control (CEC).

Additionally, the ‘HID device type’ field represents the type of the HID30. As shown in FIG. 7, according to an interface type of the HID 30,the ‘HID device type’ field may have a value corresponding to one of akeyboard, a mouse, a touch pad, a joystick, and a motion sensor.

The ‘HID value’ field includes a user input received from the HID 30,and as shown in FIG. 8, may include the user input in a format definedby a standard such as Bluetooth, ZigBee, or USB.

That is, the user input in the ‘HID value’ field may have the sameformat as a user input received from the HID 30.

For example, the sink device 20 may include a format received from theHID 30 in the ‘HID value’ field as it is, without processes for parsinga user input received from the HID 30 and converting it to anotherformat.

In more detail, as shown in FIG. 8, a user input in the ‘HID value’field may have a HID format defined by a USB standard.

In an existing USB standard, the HID 30 may deliver information betweena USB device and a USB host through a data structure called a report. Inthe USB device, a report transmitted to a USB host is called an inputreport, and a report transmitted from a USB host to a USB device iscalled an output report.

Additionally, there is a report for setting a method of operating a USBdevice, and this is called a feature report. Data transmission betweenthe HID 30 and a device driver is performed through control pipe,interrupt in pipe, and interrupt out pipe. Also, the input report of akeyboard or a mouse may be generally transmitted through interrupt inputpipe.

Moreover, widely used operation information such as key input of akeyboard or button press of a mouse may be standardized and built in anHID driver. Also, the HID 30 uses a predetermined data structure calleda report descriptor in order to match a specific usage to a controloperation such as a specific key or button and notify it to a USB host.

That is, when the HID 30 transmits user information in a formataccording to the USB standard to the sink device 20, the sink 20 mayinclude the user input in the ‘HID value’ field of the HID user inputinformation by using the received format according to the USB standardas it is.

In this case, the format of the user input in the ‘HID value’ field maybe one of the input report, the output report, the feature report, andthe report descriptor, according to the existing USB standard.

The configuration of the HID user input information described withreference to FIGS. 5 to 8 is just one example, and thus, the presentinvention is not limited thereto. For example, some of the fieldsconstituting the HID user input information may be omitted, or newfields may be applied to the HID user input information.

Referring to FIG. 9, the HID user input information delivered from thesink device 20 to the source device 10 may include ‘HID interface type’,‘HID device type’, and ‘HID value’ fields. Since the fields areidentical to those described with reference to FIGS. 5 to 8, theirdetailed descriptions are omitted.

Referring to FIG. 10, the ‘HID interface type’ field may represent‘Usage’ and ‘HID Interface Type’. For example, the first 2 bits of the‘HID interface type’ field includes information on usage of the HID userinput information and the remaining 6 bits include information on theinterface type of the HID 30.

Referring to FIG. 11, the ‘Usage’ of the ‘HID interface type’ fieldrepresents whether the HID user input information delivered to thesource device 10 includes data or control according to a value of the‘Usage’. That is, the ‘Usage’ may represent whether the HID user inputinformation delivers data according to user input through the HID 30, orinformation on the user input data.

As a result, the ‘Usage’ represents the usage of the ‘HID value’ fieldincluding the user input, and the usage of the ‘HID value’ field may bedetermined according to a format of a user input received from the HID30.

For example, when the sink device 20 receives user information accordingto the USB standard, the format of the user input in the ‘HID value’field may be one of the input report, the output report, the featurereport, and the report descriptor according to an existing USB standard.Accordingly, the ‘Usage’ may represent one of the formats of the userinput as the usage of the ‘HID value’ field.

Moreover, the ‘Usage’, as shown in FIG. 10, may not be included in the‘HID interface type’ field, and may be included in the HID user inputinformation delivered from the sink device 20 to the source device 10,as an additional field.

Moreover, although the case in which the HID user input information isconfigured with an action frame and is delivered from the sink device 20to the source device 10 is described as one example according to anembodiment of the present invention, the present invention is notlimited thereto. Thus, the HID user input information may be deliveredto the source device 10 according to various methods in addition to theabove method.

According to an embodiment of the present invention, the sink device 20may deliver the received HID format as it is to the source device 10without processes such as a conversion operation on a user inputreceived from the HID 30.

In more detail, the sink device 20 delivers the user input in an HIDformat to the source device 10 in addition to information on the typeand interface type of the HID 30 without a parsing operation torecognize detailed content on the user input received from the HID 30,i.e., an HID command. Therefore, the source device 10 may operate as ifit were directly connected to the HID 30.

FIG. 12 is a view illustrating operations for delivering a user input ofa source device, a sink device, and HIDs according to a first embodimentof the present invention.

Referring to FIG. 12, the source device 10 and the sink device 20 mayinclude an OS/Device driver for performing each device operation, an HIDMAC/PHY for processing a user input received from the HID 30, and a WFDMAC/802.11 PHY for processing a transmission signal according to awireless network connection.

Moreover, the HID 30 may include an application for receiving a commandfrom a user and an HID MAC/PHY for processing the user command accordingto a specific format such as a USB, Bluetooth, or ZigBee format.

The HID PHY of the sink device 20 may receive a user input in an HIDformat as being connected to the HID PHY of the HID 30 via an HIDinterface such as USB, Bluetooth, or ZigBee.

The received user input is processed through the OS/Device Driver of thesink device 20, and the OS/Device Driver includes the received HIDformat as it is in the HID user input information, and then transmits itto the source device 10 via the 802.11 PHY, without performing anadditional conversion operation on the user input received from the HID30.

In addition, the WFD MAC of the source device 10 obtains the user inputfrom the HID user input information received from the sink device 20,and delivers it to the OS/Device Driver. Then, the OS/Device Driverprocesses the obtained user input to perform an operation correspondingthereto.

FIG. 13 is a view illustrating a format of HID user input informationtransmitted to a source device. Description of the same frame as thatdescribed with reference to FIGS. 5 to 11 among frame formats below willbe omitted.

Referring to FIG. 13, an action frame for delivering a user input thatthe sink device 20 receives from the HID 30 to the source device 10includes the ‘Subelement ID’, ‘Length’, ‘HID ID’, ‘HID interface type’,‘HID device type’, and ‘HID value’ fields, as mentioned above.

For example, when the HID 30 is a USB mouse, a value of the ‘HID ID’field is set to ‘0’, a value of the ‘HID device type’ field is set to‘1’, and a value of the ‘HID interface type’ field is set to ‘1’.

Moreover, the ‘HID value’ field includes the received HID format as itis without an additional conversion process on a user input receivedfrom the HID 30, and for example, a user input in the ‘HID value’ fieldmay have a format defined by the USB standard as shown in FIG. 13.

The format of the ‘HID value’ field shown in FIG. 13 is a format formultibyte numeric values in reports that the HID 30 transmits in anexisting standard.

According to another embodiment of the present invention, a user inputreceived from the HID 30 is encapsulated into an IP packet via TCP/IPand delivered to the source device 10.

That is, the sink device 20 packetizes a user input received from theHID 30 by using the received HID format as it is, so as to generate anIP packet to be transmitted to the source device 10, and then, transmitsthe generated IP packet to the source device 10 via TCP/IP.

FIG. 14 is a block diagram illustrating operations for delivering a userinput of a source device, a sink device, and HIDs according to a secondembodiment of the present invention. FIG. 15 is a view illustrating aformat of HID user input information transmitted to the source device 10according to a second embodiment of the present invention.

Referring to FIGS. 14 and 15, the sink device 20 receives a user inputfrom the HID 30, and the received user input is packetized into an IPpacket through a TCP/IP block and then is delivered to the source device10 via TCP/IP.

Moreover, the IP packet delivered to the source device 10 may include IPHeader, TCP Header, and TCP Payload. The HID user input informationdescribed with reference to FIGS. 5 to 11 may be included in the TCPPayload.

For example, as shown in FIG. 15, ‘Length’, ‘HID ID’, ‘HID interfacetype’, ‘HID device type’, and ‘HID value’ fields are included in the TCPPayload part in the IP packet delivered to the source device 10, and thereceived HID format is included as it is in the ‘HID value’ fieldwithout a conversion process on the user input received from the HID 30.

Furthermore, the IP packet delivered to the source device 10 isseparated through a TCP/IP block, so that a user input received from theHID 30 to the sink device 20 may be obtained, and an operationcorresponding to the user input may be performed by application.

Although the case in which a user input received from the HID 30 isencapsulated via TCP/IP is used as one example according to anembodiment of the present invention, the present invention is notlimited thereto. For example, the user input may be encapsulated viaRTSP/TCP/IP, UDP/IP, or RTP/UDP/IP.

Referring to FIG. 16, when a user input received from the HID 30 isencapsulated via RTSP/TCP/IP, the IP packet delivered to the sourcedevice 10 may include an IP Header, a TCP Header, an RTSP Header, and anRTSP Payload. The HID user input information described with reference toFIGS. 5 to 11 may be included in the RTSP Payload.

Referring to FIG. 17, when a user input received from the HID 30 isencapsulated via UDP/IP, the IP packet delivered to the source device 10may include an IP Header, a UDP Header, and a UDP Payload. The HID userinput information described with reference to FIGS. 5 to 11 may beincluded in the UDP Payload.

Additionally, referring to FIG. 18, when a user input received from theHID 30 is encapsulated via RTP/UDP/IP, the IP packet delivered to thesource device 10 may include an IP Header, a UDP Header, an RTP Header,and a RTP Payload. The HID user input information described withreference to FIGS. 5 to 11 may be included in the RTP Payload.

Moreover, in relation to the IP packet described with reference to FIGS.15 to 18, a format of HID user input information in the payload part(that is, TCP Payload, RTSP Payload, UDP Payload or RTP Payload) may bechanged.

For example, as shown in FIG. 19, HID user input information in a TCPPayload part in an IP packet delivered to the source device 10 mayinclude the ‘HID interface type’, ‘HID device type’, and ‘HID value’fields described with reference to FIGS. 9 to 11, and also may furtherinclude information on the ‘Usage’ of corresponding HID user inputinformation.

FIG. 20 is a block diagram illustrating operations for delivering a userinput of a source device, a sink device, and HIDs according to a thirdembodiment of the present invention. Description of the sameconfiguration as that described with reference to FIGS. 1 to 19 amongconfigurations of the devices of FIG. 20 below will be omitted.

Referring to FIG. 20, a new P2P channel for delivering the user inputmay be allocated between the HID 30 and the source device 10.

For example, the HID 30 is connected to a client of the source device10, i.e., a Group Owner (GO) of a P2P group, to configure a P2P channelfor transmitting the user input during P2P connection.

Or, session pairing occurs in a P2P group via a session between thesource device 10 and the sink device 20, and the HID 30 joins the P2Pgroup as a client to transmit a user input to a P2P data frame.

The invention can also be embodied as computer readable codes on acomputer readable recording medium. The computer readable recordingmedium is any data storage device that can store data which can bethereafter read by a computer system. Examples of the computer readablerecording medium include read-only memory (ROM), random-access memory(RAM), CD-ROMs, magnetic tapes, floppy disks, and optical data storagedevices , and carrier waves (such as data transmission through theInternet).

The computer readable recording medium can also be distributed overnetwork coupled computer systems so that the computer readable code isstored and executed in a distributed fashion. Also, functional programs,codes, and code segments for accomplishing the present invention can beeasily construed by programmers skilled in the art to which the presentinvention pertains.

Although embodiments have been described with reference to a number ofillustrative embodiments thereof, it should be understood that numerousother modifications and embodiments can be devised by those skilled inthe art that will fall within the spirit and scope of the principles ofthis disclosure. More particularly, various variations and modificationsare possible in the component parts and/or arrangements of the subjectcombination arrangement within the scope of the disclosure, the drawingsand the appended claims. In addition to variations and modifications inthe component parts and/or arrangements, alternative uses will also beapparent to those skilled in the art.

1-15. (canceled)
 16. A method for a sink device to control a sourcedevice based on user input information received from a Human InterfaceDevice (HID), the method comprising: receiving, by the sink device fromthe HID, the user input information generated by the HID; delivering, bythe sink device to the source device through a user input back channelestablished between the sink device and the source device, a user inputinformation frame representing the received user input information;wherein the user input information is one of a first category and asecond category, wherein the user input information of the firstcategory is formatted within the user input information frame byconversion of the received user input information to convertedinformation based on a specific user interface coordination, and whereinthe user input information of the second category is formatted withinthe user input information frame by including the received user inputinformation in one of fields of the user input information frame. 17.The method of claim 16, wherein the sink device includes the receiveduser input information of the second category without conversion basedon the specific user interface coordination in one of fields of the userinput information frame.
 18. The method of claim 16, further comprising:receiving multimedia contents from the source device; and rendering thereceived multimedia contents.
 19. The method of claim 16, wherein theuser input information frame with the user input information of thesecond category comprises: a first field that represents a type of theHID, a second field that represents an interface type of the HID, and athird field that includes the user input information received from theHID.
 20. The method of claim 19, wherein the first field has a valuecorresponding to one of a keyboard, a mouse, a touch device, and ajoystick.
 21. The method of claim 19, wherein the second field has avalue corresponding one of infrared, USB, Bluetooth, ZigBee, and Wi-Fi.22. A sink device controlling a source device based on user inputinformation received from a Human Interface Device (HID), the sinkdevice comprising: an interface unit receiving the user inputinformation generated by the HID from the HID; and a control unitcontrolling the interface unit to deliver a user input information framerepresenting the user input information to the source device through auser input back channel established between the sink device and thesource device; wherein the user input information is one of a firstcategory and a second category, wherein the control unit formats theuser input information of the first category within the user inputinformation frame by conversion of the received user input informationto converted information based on a specific user interfacecoordination, and wherein the control units formats the user inputinformation of the second category within the user input informationframe by including the received user input information in one of fieldsof the user input information frame.
 23. The sink device of claim 22,wherein the control units includes the received user input informationof the second category without conversion based on the specific userinterface coordination in one of fields of the user input informationframe.
 24. The sink device of claim 22, wherein the sink device receivesmultimedia contents from the source device; and renders the receivedmultimedia contents.
 25. The sink device of claim 22, wherein the userinput information frame with the user input information of the secondcategory comprises: a first field that represents a type of the HID, asecond field that represents an interface type of the HID, and a thirdfield that includes the user input information received from the HID.26. The sink device of claim 25, wherein the first field has a valuecorresponding to one of a keyboard, a mouse, a touch device, and ajoystick.
 27. The sink device of claim 25, wherein the second field hasa value corresponding one of infrared, USB, Bluetooth, ZigBee, andWi-Fi.